8.6
HIGH CVSS 4.0
CVE-2026-22816
Gradle fails to disable repositories which can expose builds to malicious artifacts
Description

Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. If a Gradle build used an unresolvable host name, Gradle would continue to work as long as all dependencies could be resolved from another repository. An unresolvable host name could be caused by allowing a repository's domain name registration to lapse or typo-ing the real domain name. This behavior could allow an attacker to register a service under the host name used by the build and serve malicious artifacts. The attack requires the repository to be listed before others in the build configuration. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.

INFO

Published Date :

Jan. 16, 2026, 11:15 p.m.

Last Modified :

Jan. 16, 2026, 11:15 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-22816 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Gradle gradle
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 4.0 HIGH [email protected]
Solution
Update Gradle to version 9.3.0 or later for improved dependency resolution security.
  • Update Gradle to 9.3.0 or newer.
  • Ensure all dependency repositories are correctly configured.
  • Review repository order in build configurations.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-22816.

URL Resource
https://github.com/gradle/gradle/commit/e5707d0d8fce3d768c9c489004700d78eab1773a
https://github.com/gradle/gradle/security/advisories/GHSA-w78c-w6vf-rw82
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-22816 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-22816 weaknesses.

CAPEC-184: Software Integrity Attack Software Integrity Attack CAPEC-185: Malicious Software Download Malicious Software Download CAPEC-186: Malicious Software Update Malicious Software Update CAPEC-187: Malicious Automated Software Update via Redirection Malicious Automated Software Update via Redirection CAPEC-533: Malicious Manual Software Update Malicious Manual Software Update CAPEC-538: Open-Source Library Manipulation Open-Source Library Manipulation CAPEC-657: Malicious Automated Software Update via Spoofing Malicious Automated Software Update via Spoofing CAPEC-662: Adversary in the Browser (AiTB) Adversary in the Browser (AiTB) CAPEC-691: Spoof Open-Source Software Metadata Spoof Open-Source Software Metadata CAPEC-692: Spoof Version Control System Commit Metadata Spoof Version Control System Commit Metadata CAPEC-693: StarJacking StarJacking CAPEC-695: Repo Jacking Repo Jacking CAPEC-175: Code Inclusion Code Inclusion CAPEC-201: Serialized Data External Linking Serialized Data External Linking CAPEC-228: DTD Injection DTD Injection CAPEC-251: Local Code Inclusion Local Code Inclusion CAPEC-252: PHP Local File Inclusion PHP Local File Inclusion CAPEC-253: Remote Code Inclusion Remote Code Inclusion CAPEC-263: Force Use of Corrupted Files Force Use of Corrupted Files CAPEC-538: Open-Source Library Manipulation Open-Source Library Manipulation CAPEC-549: Local Execution of Code Local Execution of Code CAPEC-640: Inclusion of Code in Existing Process Inclusion of Code in Existing Process CAPEC-660: Root/Jailbreak Detection Evasion via Hooking Root/Jailbreak Detection Evasion via Hooking CAPEC-695: Repo Jacking Repo Jacking CAPEC-698: Install Malicious Extension Install Malicious Extension

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-22816 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-22816 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jan. 16, 2026

    Action Type Old Value New Value
    Added Description Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. If a Gradle build used an unresolvable host name, Gradle would continue to work as long as all dependencies could be resolved from another repository. An unresolvable host name could be caused by allowing a repository's domain name registration to lapse or typo-ing the real domain name. This behavior could allow an attacker to register a service under the host name used by the build and serve malicious artifacts. The attack requires the repository to be listed before others in the build configuration. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.
    Added CVSS V4.0 AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CWE CWE-494
    Added CWE CWE-829
    Added Reference https://github.com/gradle/gradle/commit/e5707d0d8fce3d768c9c489004700d78eab1773a
    Added Reference https://github.com/gradle/gradle/security/advisories/GHSA-w78c-w6vf-rw82
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 8.6
Attack Vector
Attack Complexity
Attack Requirements
Privileges Required
User Interaction
VS Confidentiality
VS Integrity
VS Availability
SS Confidentiality
SS Integrity
SS Availability